Repository navigation
Conversation
Schlage locks refuse a PIN that is already in use by answering the UserCode Set with STATUS_NOT_AVAILABLE and a code of zeros, and send no notification. The driver counted that report as a set slot, so addCredential returned success and created a user whose PIN is not on the lock, and updateCredential returned success while the old PIN stayed in place. While an add or update is waiting, a STATUS_NOT_AVAILABLE report for that slot now returns duplicate, leaves users and credentials unchanged, and clears the busy state. The legacy (lockCodes) Schlage handler is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Channel deleted. |
|
zwave-lock_coverage.xml
Minimum allowed coverage is Generated by 🐒 cobertura-action against d797c72 |
Test Results 73 files 571 suites 0s ⏱️ Results for commit d797c72. |
5 of 12 tasks
Contributor
Author
|
These changes have been merged as a part of #3373 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Schlage locks refuse a PIN that is already in use by answering the UserCode Set with STATUS_NOT_AVAILABLE and a code of zeros, and send no notification. The driver counted that report as a set slot, so addCredential returned success and created a user whose PIN is not on the lock, and updateCredential returned success while the old PIN stayed in place.
While an add or update is waiting, a STATUS_NOT_AVAILABLE report for that slot now returns duplicate, leaves users and credentials unchanged, and clears the busy state. The legacy (lockCodes) Schlage handler is unchanged.
Check all that apply
Type of Change
Checklist
Description of Change
Summary of Completed Tests